Shareware Overload Trio 2/Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO/dir40/qemm7rel.zip/QEMM7QA.TXT

Text File | 1993-06-15 | 10KB | 182 lines

                             QEMM 7
              Commonly Asked Questions and Answers



What is new in QEMM 7?

We had six objectives for QEMM 7: (1) More memory free for programs. (2)
Compatibility with the hardware advances that have occurred since QEMM 6.
(3) Performance and compatibility  enhancements for Microsoft Windows. (4)
Easier installation and finetuning. (5) MS-DOS 6-specific features. (6) More
detailed reporting (Manifest) of your system's configuration. The result is
that QEMM has been significantly enhanced in all of the above categories.
(see below)


What does QEMM 7 do for me if I already have QEMM 6?

First, more memory free for programs. The 640K area used by DOS programs
continues to get more and more cramped. As networks accommodate cross
platform computing, network drivers have gotten bigger (example Netware ODI;
TCP/IP). Multimedia means large pen drivers, sound drivers and CD ROM
drivers--all which take memory. Disk compressors and anti-virus programs also
require memory.

QEMM 7 builds upon the innovative memory management techniques incorporated
in QEMM 6 that we call Stealth. QEMM 6's Stealth feature used the EMS page
frame for ROMs, freeing 48-115K of memory for other drivers. QEMM 7 expands
its Stealth capabilities, using the EMS page frame to stealth specific
drivers--the first of which is the DOS 6 DoubleSpace driver. QEMM 7's Stealth
DoubleSpace feature frees 40K for other drivers. But the breakthrough in
QEMM 7 is that the page frame can be used to manage (rather than just fill)
the upper memory area between 640K-1MB.

In addition, QEMM 7 provides a smaller DOS footprint below 640K--resulting in
more memory (7-70K) free for programs. QEMM 7's DOS-Up feature moves the DOS
kernal, DOS data and/or DOS resources above 640K.


Second, compatibility with the newest hardware. It has been 22 months since
we introduced QEMM 6. Since then hardware has changed and advanced--
especially graphics adapters, bus-mastering controllers, CD ROMs, pen
computing and sound. A memory manager, more than any other software, needs to
accommodate new hardware drivers and devices. Over the last 22 months our
technical support kept detailed records of our user's hardware and QEMM's
compatibility with this hardware. As a result, QEMM 7 recognizes more types
of new techniques like: shadow RAM, adapter RAM, bus-mastering controllers,
suspend/resume features of battery-powered PCs, the Pentium processor, etc.


Third, smoother MS-Windows performance. QEMM 7's MS-Windows features are
mostly "under the hood", the result of experience in using Windows 3.1 with
QEMM. One small feature is that when QEMM 7 detects that you are starting up
Windows, it reserves 8-24K for Windows' buffers. The result is better
performance of DOS programs inside Windows. Manifest now detects Windows,
reports Windows information, and lets you edit Windows .INI files. QEMM's
Vidram feature gives you 700K+ for DOS text programs.


Fourth, easier still installation and fine tuning. QEMM 7 has an Express
Install feature that streamlines installation. QEMM 7's new QSetup provides
menus and online help for changing QEMM parameters and features. It also lets
you edit configuration files and provides troubleshooting tips and hints.


Fifth, MS-DOS 6-specific features.  MS-DOS 6 gives you the ability to manage
multiple CONFIG.SYS files. QEMM 7's Installation, QSetup and Optimize all
support DOS 6's multiple configuration feature. In addition, QEMM 7's Stealth
DoubleSpace feature frees 40K of the 43k memory addresses used by
DoubleSpace, making this memory available for other drivers and TSRs.


Sixth, a more robust Manifest. Manifest now gives you information on
networks, battery, MS-Windows and Pentium, plus additions to its other
reporting categories. Using Manifest you can now edit configuration files.


Seventh, lots of little things. Install and Optimize accommodate Stacker and
SuperStor. DPMI Host provides built-in DPMI services with virtual memory.
QEMM 7 is 32-bit for faster performance. There is enhanced Stealth testing.
QEMM has a smaller footprint below 640K. ROM holes are detected to give
maximum memory when a page frame is not reserved. On IBM PCs the memory
reserved for IBM BASIC can be reclaimed.


Why do I need QEMM when DOS 6's MemMaker is free?

For DOS users the key to system performance is memory management. Memory is
the most precious resource of the DOS PC. It is the resource which has the
greatest limitations and which is the hardest to understand (for power users
as well as novice users). If you compare a DOS PC to a high powered car, good
memory management is akin to keeping the car tuned. It is essential if you
want smooth performance.

Microsoft has historically viewed compatibility as the responsibility of
non-Microsoft developers (hardware and software). What this means is that
Microsoft expects software and hardware to be compatible with its
products--not vice versa and this is the reason why the DOS user's legacy in
software and hardware often is not compatible with a new Microsoft release.
Quarterdeck in contrast has a commitment to making its products compatible
with the hardware and software of our users. And it is a major focus of QEMM.
The utilities in DOS 6 require precious memory. DoubleSpace takes 43K; VSafe
takes 43K, Undelete takes 13K, Interlink takes 9K--all of which mean that
every user needs some automatic way of managing memory. MemMaker does that,
but with limitations. It ignores multiple configurations and called batch
files. It finds the most upper memory when an EMS page frame is not
reserved--thus restricting WordPerfect 5, Lotus 1-2-3 r2.x, Foxpro and other
application programs, most of the "hot" games, network drivers and other
devices from using expanded memory. And even then the upper memory made
available is less than that made available by QEMM without a page frame--not
to mention Stealth.

But the most important reason for using QEMM 7 with DOS 6 is to set up your
PC in the most flexible and expandable way--so that programs and drivers can
be added without suddenly encountering "out of memory" conditions or
compatibility problems. Memory needs to be transparent--no matter what you
want to do.


Why does Quarterdeck like the EMS page frame so much?

In 1985 Intel, Lotus and Microsoft specified a way of expanding the amount of
memory a DOS program could use. This specification was called the Expanded
Memory Specification (EMS). Key to EMS was a 64K area reserved (usually above
640K) as paged memory, i.e. memory that could be accessed and used
instantanteously by one or several programs.

This paged memory was (and still is) used by Lotus and Borland to increase
the size of their spreadsheets, WordPerfect to increase the size of documents
and Borland and Fox to increase the size of databases. It is used by game
programs to speed up the performance of their graphics screens. It is used by
networks, such as Novell Netware, DEC Pathworks, and IBM LAN Server, to
reduce the network driver footprint. It is used by Microsoft to reduce the
footprint of its MSCDEX CD ROM and its VSafe anti-virus drivers. And it is
(and has been since 1985) used by Quarterdeck for DOS multitasking.

EMS is important because it provides a window into memory. It serves to break
through the DOS 640K barrier without major new development. It is an accepted
industry standard. And it works. In fact it has worked reliably since 1985.
Surprising to many, it is often faster than accessing the protected mode of
the PC.

We at Quarterdeck like EMS because we understand its power. Our use of
expanded memory in DESQview lets us multitask DOS programs. Our use of
expanded memory with Stealth in QEMM lets us multitask ROM code, the DOS 6
DoubleSpace driver and drivers that use EMS. And it provides us with a known,
proven way of breaking through the DOS 640K memory limitation as multimedia
and networking require more and more DOS memory. To us it's the window into
"expanded" memory management.


Is the stealthing of ROMs safe?

Yes it is--but the amount of memory that QEMM's Stealth ROM feature makes
available does vary from one PC brand to another--and can, on some PCs, be
0K. When QEMM's Optimize detects that you have more drivers and TSRs than fit
in memory above 640K, it determines whether the Stealth ROM feature will work
on your PC. First it tries to make available the maximum amount of memory by
using the Stealth Mapping method. If it detects memory conflicts it tries the
Stealth Frame method. This method makes available 48K of memory in contrast
to 115K with Stealth Mapping. The detection in QEMM 7 will also try to assess
if there are any memory addresses that can be excluded and still use Stealth
Mapping.

In doing the detection, your system can hang. But on reboot you will find
that Stealth cannot be used. That is the purpose of the detection. If you add
Stealth Mapping to the QEMM command line without doing Stealth detection,
your system may hang if there are memory conflicts. In this case you will
have to troubleshoot to see if any memory addresses can be excluded or if you
have to use the Stealth Frame method or no Stealth at all.


Can I use QEMM without a page frame?

Of course. Since QEMM's default setup is with the page frame on, you will
have to install QEMM using its Advanced Install option or after installation
run QEMM's QSetup program and turn the page frame off.

QEMM maximizes the amount of memory available even when you do not use a page
frame--for it finds holes in ROMs that are not being used.